Error 403: Forbidden

Error Code

enl-api-403

What does this error mean?

The request was correctly authenticated but rejected because your organization does not have the required feature enabled. This is not a credential problem — your API key is valid. It is an entitlement / subscription problem.

Common causes of Error 403

1. Field-level feature flag (V2-12387): You sent a field on POST or PUT /transactions whose feature is not enabled for your organization. Example response:

   {
     "error": "enl-api-403",
     "message": "Forbidden. Feature not available.",
     "detail": "'assignedGroupId' requires the 'teamAssignment' feature, which is not enabled for your organization."
   }

   Gated field	Required feature flag
   useReplyTo, replyToEmail	enableReplyTo
   assignedGroupId	teamAssignment
   allowSignerNameEdit	signersNameEdit

   The check applies whether the field is set to a value or to null (clear) — supplying the field at all is what triggers the check.

2. Route-level feature flag: The entire endpoint is gated. For example, GET /teams returns 403 enl-api-403 when the teamAssignment feature flag is not enabled.

3. Organization context missing: The bearer token did not resolve to an organization. Confirm the API key still maps to a valid organization.

How to resolve Error 403

1. Identify the gated field — read the detail field in the response; it names the offending field and the required feature flag.
2. Remove the field from your request, or
3. Contact your account manager to have the feature flag enabled for your organization.

Contact Support Team

Additional Resources

• List Teams — endpoint for discovering assignedGroupId values (also gated by teamAssignment).
• Update a Transaction — full reference of new fields and their flags.

For more information about the Stewart Sign API, visit the official documentation.